Skip to content

fix(fms): waypoint display conditions at enroute ranges#10547

Open
tracernz wants to merge 11 commits intoflybywiresim:masterfrom
tracernz:mrc-nd-wpt
Open

fix(fms): waypoint display conditions at enroute ranges#10547
tracernz wants to merge 11 commits intoflybywiresim:masterfrom
tracernz:mrc-nd-wpt

Conversation

@tracernz
Copy link
Copy Markdown
Member

@tracernz tracernz commented Feb 8, 2026

Fixes #[issue_no]

Summary of Changes

  • Don't show terminal waypoints on the EFIS WPT overlay when in enroute ranges.
  • Do show TO WPT, flight plan waypoints either side of lateral discontinuities, and at the boundary between departure/arrival/enroute.
  • Fix type errors in EfisSymbols and enable strict mode.

Screenshots (if necessary)

NZCH.RW02 GUTBU2P.GRETA Y393 WARDS WARD6A UMAGA.ILS34.NZWN
GRETA and WARDS are either side of a discontinuity in the first pic, and the enroute boundaries in the second pic...
Before:
Screenshot 2026-02-08 210904
image

After:
Screenshot 2026-02-08 210225
Screenshot 2026-02-08 210253

References

Additional context

Discord username (if different from GitHub):

Testing instructions

Either plane is fine.
Enter a flightplan in stages, and check in PLAN mode with range at 160 or 320 that the waypoints either side of discontinuities are shown on the ND, and at the boundary between the departure and enroute, and arrival and enroute are shown when completed. Takeoff with the ND on 160 NM range in ARC mode and make sure the TO WPT (top right of ND) is always shown on the ND map.

How to download the PR for QA

Every new commit to this PR will cause new A32NX and A380X artifacts to be created, built, and uploaded.

  1. Make sure you are signed in to GitHub
  2. Click on the Checks tab on the PR
  3. On the left side, find and click on the PR Build tab
  4. Click on either flybywire-aircraft-a320-neo, flybywire-aircraft-a380-842 (4K) or flybywire-aircraft-a380-842 (8K) download link at the bottom of the page

@tracernz tracernz added this to the v0.15.0 milestone Feb 8, 2026
@github-project-automation github-project-automation Bot moved this to 🟡 Code Review: Ready for Review in Quality Assurance Feb 8, 2026
@tracernz
Copy link
Copy Markdown
Member Author

Need to fix imports after master merge.. otherwise still RTR.

@github-project-automation github-project-automation Bot moved this from 🟡 Code Review: Ready for Review to 🟣 QA Review: Ready to Test in Quality Assurance Apr 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: 🟣 QA Review: Ready to Test

Development

Successfully merging this pull request may close these issues.

2 participants